Android 15 may arrive with a strong new privateness function that would assist forestall customers from leaking their private info whereas sharing their display screen, in response to a report. The subsequent model of Google’s smartphone working system — anticipated to reach within the second half of 2024 — may obscure sure components of the display screen, similar to password fields or delicate notifications, from being displayed when display screen sharing is enabled. Google may additionally enable customers to disable these protections on their Android smartphone.
As per an Android Police report, the newest Android 15 Beta 1.1 launch accommodates a brand new toggle within the Developer choices menu titled Disable display screen share protections. The outline for the toggle explains that the setting will disable system protections for “delicate app content material” when a person shares their display screen sooner or later. Sadly, the function is but to be enabled by Google on the newest Android 15 beta.
The publication additionally noticed a brand new API on the newest Android 15 beta launch that permits apps with customized digital views, WebView, and Jetpack Compose to entry a delicate content material safety function. The function may reportedly enable the working system to dam particular fields that present delicate info, similar to passwords or e-mail addresses.
It is presently unclear how telephones operating on Android 15 will decide what components of the display screen to obscure throughout a display screen sharing session. Nonetheless, the function may additionally defend customers from scammers who persuade customers to share their screens to achieve entry to their passwords, one-time passwords (OTPs), or two-factor authentication codes.
The function is reportedly disabled on Android 15 Beta 1.1, which implies it can’t be examined by customers who’ve flashed the primary public beta on their Pixel telephones. It may both be enabled on Android 15 Beta 2, or might be unveiled by the corporate at Google I/O in Might earlier than it’s rolled out to beta testers, in response to the report.
